Node / public / MeshChatX rns://06a54b505bb67b25ef3f8097e8001edc/public/MeshChatX

󰉖 Files • 󰏗 Releases (3) • 󱌣 Work (0) • 󰋚 Commits (2261) • 󰘬 Branches (2) • 󰓼 Tags (53) • 󰋑 Thanks (18)

• Uses LXST for calls

• Integrates RRC

• Expanded tools

• Map w/ MBTiles support, remote KMZ/KML/GeoJSON overlays (NomadNet T383838/file/ and RNGit sparse fetch)

• Panes and Tabs

• Replaced Peewee ORM with raw SQL.

• Replaced Axios with native fetch.

• Uses Electron 41.x (bundled Node 24 runtime).

• .whls ships with webserver and built-in frontend assets for more deployment options.

• i18n

• PNPM and UV for dependency management.

• Python T383838>=3.11 (from T383838pyproject.toml)

• Node.js T383838>=24 (from T383838package.json T383838engines)

• pnpm T38383811.1.2 (from T383838package.json T383838packageManager)

• UV (used by T383838Taskfile.yml and CI workflows)

Safari 16.4 or later, Chrome 111 or later, Firefox 128 or later (bundled web UI).

T282828

Use the method that matches your environment and packaging preference.

Notes:

• GitHub Actions builds tagged releases (Linux wheel/AppImage/deb/rpm, Windows, macOS, Flatpak, Android APKs when the tag is on T383838dev or T383838master, SLSA, draft release) in one run via T383838.github/workflows/build-release.yml; the container image via T383838.github/workflows/docker.yml. Branch and PR Android CI stays in T383838.github/workflows/android-build.yml.

• Linux T383838x64 and T383838arm64 AppImage + DEB are built on GitHub; RPM is attempted and uploaded when produced.

• Docker Hub: T383838quad4io/meshchatx

• GHCR: T383838ghcr.io/quad4-software/meshchatx

• Variants: default tags (for example T383838:latest) are the standard Alpine image. Use T383838-hardened for the Chainguard/Wolfi image, or T383838-extra for Alpine plus i2pd and yggdrasil (for example T383838:latest-extra, built from the same T383838Dockerfile with T383838VARIANT=extra).

T282828

T282828

You can substitute T383838quad4io/meshchatx:latest for the image if you prefer Docker Hub.

Default compose file maps:

• T383838127.0.0.1:8000 on host -> container port T3838388000

• Docker named volume T383838meshchatx-config -> T383838/config for persistence (works with the image T383838meshchat user, UID 1000, without bind-mount permission fixes)

If you want data under a host path (for example T383838./meshchat-config), replace the volume line with T383838-v "$(pwd)/meshchat-config:/config" (Compose: change the service T383838volumes entry to that bind path). The container runs as UID 1000; the host directory must be writable by that uid (typical fix: T383838sudo chown -R 1000:1000 ./meshchat-config). If the directory is empty on first run, create it first so Docker does not create it as root-only.

T282828

1. Download T383838ReticulumMeshChatX-v<version>-linux-<arch>.AppImage from releases.

2. Make it executable and run:

T282828

1. Download T383838ReticulumMeshChatX-v<version>-linux-<arch>.deb.

2. Install:

T282828

1. Download T383838ReticulumMeshChatX-v<version>-linux-<arch>.rpm if present in the release.

2. Install with your distro tool:

T282828

Release wheels include the built web assets.

T282828

T383838pipx is also supported:

T282828

Use this when developing or when you need a local custom build.

T282828

Notes on the install commands above:

• T383838pnpm install --frozen-lockfile refuses to update T383838pnpm-lock.yaml and fails if the lockfile does not match T383838package.json. This is what blocks an unexpected upstream version from being silently pulled in.

• T383838verify-store-integrity=true is also set in the project T383838pnpm-workspace.yaml; the explicit T383838pnpm config set line above just hardens the user-level config too.

• Lifecycle scripts (T383838preinstall/T383838postinstall) are blocked by default in pnpm v11+. Only the packages listed under T383838allowBuilds in T383838pnpm-workspace.yaml are allowed to run install scripts (currently T383838electron, T383838electron-winstaller, T383838esbuild).

• T383838uv lock --check fails fast if T383838uv.lock is out of sync with T383838pyproject.toml; T383838uv sync then resolves only from the lockfile.

• For a strict lockfile-only UV install (no implicit lockfile refresh), pin UV with T383838pip install "uv==0.11.15" to match what CI uses.

If you intentionally want to update dependencies, run T383838pnpm update / T383838uv lock in a dedicated commit and review the resulting lockfile diff before pushing.

To run the native T383838meshchatx binary (alias: T383838meshchat) with extra filesystem isolation, you can use Firejail or Bubblewrap (T383838bwrap) while keeping normal network access for Reticulum and the web UI. Full examples (pip/pipx, Poetry, USB serial notes) are in:

• docs/meshchatx_linux_sandbox.md

The same page appears in the in-app Documentation list (MeshChatX docs) when served from the bundled or synced T383838meshchatx-docs files.

The emoji picker renders standard Unicode emoji using your system fonts (Electron/Chromium). If emoji show as empty squares (“tofu”), install a color emoji package and restart the app.

After installing, run T383838fc-cache -fv if glyphs still fail until the next login. Optional: T383838noto-fonts for broader symbol coverage on minimal installs.

Calls and voice attachments use the microphone through Chromium inside the desktop app. If the UI shows no access or getUserMedia fails, check Windows privacy first (this is a frequent cause for “classic” Win32 apps, including Electron):

1. Press Win + R, paste T383838ms-settings:privacy-microphone, press Enter.

2. Turn Microphone access on.

3. Enable Let desktop apps access your microphone (wording may vary slightly by Windows version).

4. Ensure MeshChatX is not denied under Choose which apps can access your microphone if that list appears.

Also confirm the app is not muted in Settings → System → Sound and that a working input device is selected.

MeshChatX supports two levels of offline building:

1. Cached offline builds: you already ran T383838make install once and have T383838node_modules/, T383838.venv/, and local caches.

2. Air-gapped (zero-network) builds: the machine has never had internet. You create an offline bundle on a networked machine and transfer it.

Set T383838MESHCHATX_OFFLINE_BUILD=1 before running any build command. This skips all network fetches (micron-parser-go WASM, Reticulum manual, repository wheels) and runs package managers in offline mode. If a required cached asset is missing, the build fails with a clear error instead of hanging.

T282828

│ Note: Cached offline mode only skips build-time network access. The first T383838make install must be

│ run online (or with pre-populated caches) so that T383838pnpm and T383838uv have the packages available

│ locally.

For machines with no internet access at all, create an offline bundle on a networked machine and transfer it.

T282828

T282828

The bundle is platform-specific because it contains native binaries (Electron, esbuild, etc.). Create it on the same OS/architecture as the air-gapped build host.

Prerequisites on the air-gapped machine: T383838node, T383838pnpm, T383838uv, and T383838python3 must be installed (the bundle provides all dependencies and caches, not the toolchain itself).

│ Android builds: The offline bundle does not include Android Chaquopy wheels. Build those

│ separately on an online machine (T383838bash scripts/build-android-wheels-local.sh) and copy

│ T383838android/vendor/ to the air-gapped host alongside the project. Then run Gradle with

│ T383838MESHCHATX_OFFLINE_BUILD=1.

These scripts are defined in T383838package.json and T383838Taskfile.yml.

T282828

T282828

T282828

Or through Task:

T282828

T383838Dockerfile.build runs the same shell-driven steps CI uses (Poetry, pnpm, T383838task, packaging APT deps). It is oriented toward linux/amd64 (NodeSource amd64 tarball, Task amd64 binary). Default target is everything; override with a build arg.

Targets for T383838MESHCHATX_BUILD_TARGETS: T383838all (default), T383838wheel, or T383838electron (AppImage + deb for x64 and arm64, best-effort RPM, no wheel).

Build:

T282828

Build only a wheel:

T282828

Copy T383838/artifacts from the finished image to the host:

T282828

• Docker image: T383838amd64, T383838arm64

• Linux AppImage: T383838x64, T383838arm64

• Linux DEB: T383838x64, T383838arm64

• Windows: T383838x64, T383838arm64 (build scripts available)

• macOS: build scripts available (T383838arm64, T383838universal) for local build environments

• Android: universal APK only (see android/README.md)

MeshChatX supports native Android APK builds (not only Termux).

From repo root:

T282828

Offline Android builds are supported by setting T383838MESHCHATX_OFFLINE_BUILD=1:

T282828

This skips the repository wheels fetch step. The T383838android/vendor/ wheels and T383838meshchatx/public/repository-server-bundled/bundled/ must already be present.

There is a single Android variant. Gradle syncs the full T383838meshchatx/ tree into T383838app/src/main/python/meshchatx/, including the offline repository wheel bundle. Published and documented builds use universal packaging only: one debug APK and one release APK per run, each containing the native ABIs configured in T383838android/app/build.gradle.

• Debug: T383838android/app/build/outputs/apk/debug/app-debug.apk

• Release: T383838android/app/build/outputs/apk/release/app-release-unsigned.apk

Notes:

• Release outputs are unsigned by default unless you configure signing (T383838scripts/sign-android-apks.sh).

• Native ABIs embedded in the universal APK follow T383838android/app/build.gradle (including T383838armeabi-v7a when enabled). Building wheels for T383838armeabi-v7a needs an Android SDK on T383838ANDROID_HOME (see T383838android/README.md).

• If repo root T383838dist/reticulum_meshchatx-*.whl exists (for example from T383838python -m build --wheel -o dist .), bundled repository refresh prefers that wheel over PyPI for the MeshChatX package. CI builds that wheel before the Android Gradle step.

Additional docs:

• docs/meshchatx_on_android_with_termux.md

• android/README.md

MeshChatX supports both CLI args and env vars.

Common tasks from T383838Taskfile.yml:

T282828

T383838Makefile targets are thin shims that delegate to T383838task (same commands as above):

Current version in this repo is T3838384.8.2.

• T383838package.json T383838version is the only value you edit for a release bump.

• Run T383838pnpm run version:sync (also run at the start of T383838pnpm run build) to propagate that version into T383838pyproject.toml, T383838meshchatx/src/version.py, T383838THIRD_PARTY_NOTICES.txt (product line), README / lang/README.\* “current version” lines, T383838docs/meshchatx_on_raspberry_pi.md pipx example, and T383838packaging/arch/PKGBUILD helpers.

• T383838meshchatx.__version__ is read from T383838meshchatx/src/version.py without importing T383838meshchatx.src, so a plain T383838import meshchatx stays lightweight.

• Changelog entries stay manual when you cut a release.

If MeshChatX fails to start with errors such as T383838database disk image is malformed, T383838DatabaseError, or corrupted ratchet data, the desktop crash screen now offers recovery actions:

• Restore latest backup from T383838database-backups/ or T383838snapshots/ inside your MeshChatX storage folder

• Choose backup file to restore a T383838.zip you saved elsewhere

• Try auto-repair to relaunch with T383838--auto-recover (SQLite checkpoint / integrity pass)

• Emergency mode to open the app without the database so you can export data from About when possible

• Copy reset instructions with the exact folders to delete for a clean reinstall

Legacy Reticulum MeshChat data may still exist at T383838~/.reticulum-meshchat/ (or the Windows equivalent).

Automatic database backups are written to:

T383838database-backups/ inside the MeshChatX storage folder when the app has run successfully before.

Quit MeshChatX completely. On Windows, also end T383838ReticulumMeshChatX.exe in Task Manager if it is still running. Then delete the MeshChatX storage folder and the Reticulum config folder for your install type (see table above). This removes your local identity, messages, contacts, path cache, and ratchet state. The next launch creates a new identity unless you restore from a backup first.

T282828

T282828

Custom installs: if you pass T383838--storage-dir or T383838--reticulum-config-dir, remove those directories instead of the defaults.

When the backend can start briefly or you run from source:

T282828

Security and integrity details:

• SECURITY.md

• LEGAL.md

• Built-in integrity checks and HTTPS/WSS defaults in app runtime.

• CI and release builds on GitHub Actions.

My workflow: ArgosTranslate -> Local LLM (Qwen 3 + Gemma 4)

People are then welcome to submit fixes to me via LXMF (T383838f489752fbef161c64d65e385a4e9fc74) or wherever you can contact me.

Locale discovery is automatic. Add a new file under T383838meshchatx/src/frontend/locales/ (for example T383838xx.json) with the same keys as T383838en.json and a top-level T383838_languageName string for the label shown in the language selector. You can copy T383838en.json and translate every value by hand; machine-assisted generation is optional and never required.

Optional: Argos Translate bootstrap -- If you want a machine-generated first draft from T383838en.json, you can use T383838scripts/argos_translate.py. It handles formatting, color output, and helps protect interpolation variables (like T383838{count}) from accidental edits.

T282828

After any machine-assisted pass, have an LLM or a human reviewer verify grammar, context, and tone (for example formal vs informal).

Run T383838pnpm test -- tests/frontend/i18n.test.js --run to verify key parity with T383838en.json.

No other code changes are required. The app, language selector, and tests all discover locales from the T383838meshchatx/src/frontend/locales/ directory at build time.

Donations are voluntary. They help fund time and effort to develop this app.

Ways to give: donate.md (Monero, Ko-Fi, Buy Me a Coffee).

• Liam Cottle - Original Reticulum MeshChat

• RFnexus - micron parser JavaScript work

• markqvist - Reticulum, LXMF, LXST

Project-owned portions are licensed under 0BSD.

Original upstream portions from Reticulum MeshChat remain under MIT.

See LICENSE for full text and notices.